Sometimes it is ok that babl includes are included directly and not
through babl.h, like when we generate GObject introspection files.
The important thing is just that users of the babl API don't begin to
include headers we don't guarantee to always exist, and
BABL_IS_BEING_COMPILED doesn't obstruct this goal.
--libtool="$(LIBTOOL)" \
--output $@ \
--pkg babl \
+ -DBABL_IS_BEING_COMPILED \
-I$(top_srcdir) \
-I$(top_builddir) \
$(library_include_HEADERS) \
#ifndef _BABL_MACROS_H
#define _BABL_MACROS_H
-#ifndef BABL_INSIDE_BABL_H
+#if !defined(BABL_INSIDE_BABL_H) && !defined(BABL_IS_BEING_COMPILED)
#error "babl-version.h must not be included directly, include babl.h instead."
#endif
#ifndef _BABL_TYPES_H
#define _BABL_TYPES_H
-#ifndef BABL_INSIDE_BABL_H
+#if !defined(BABL_INSIDE_BABL_H) && !defined(BABL_IS_BEING_COMPILED)
#error "babl-version.h must not be included directly, include babl.h instead."
#endif
#ifndef _BABL_VERSION_H
#define _BABL_VERSION_H
-#ifndef BABL_INSIDE_BABL_H
+#if !defined(BABL_INSIDE_BABL_H) && !defined(BABL_IS_BEING_COMPILED)
#error "babl-version.h must not be included directly, include babl.h instead."
#endif